Skip to content

chore: enforce release branch for latest channel publishing#143

Merged
miguelangaranocurrents merged 2 commits into
mainfrom
maxi/enforce-release-branch-for-latest-publish
Jun 5, 2026
Merged

chore: enforce release branch for latest channel publishing#143
miguelangaranocurrents merged 2 commits into
mainfrom
maxi/enforce-release-branch-for-latest-publish

Conversation

@maxigimenez

@maxigimenez maxigimenez commented Jun 3, 2026 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Contributor

Add validation to ensure latest channel publishes only from release/* branches.

Made with Cursor

Summary by CodeRabbit

  • Chores
    • Added validation to the publish workflow to restrict publishing to the "latest" channel to proper release branches/tags.
    • Updated the completion Slack message for the "latest" channel to include a rocket emoji (🚀) before "Release".

@maxigimenez @cursoragent
chore: enforce release branch for latest channel publishing
04de7eb 
Add validation to ensure latest channel publishes only from release/* branches.

Co-authored-by: Cursor <cursoragent@cursor.com>
@coderabbitai

coderabbitai Bot commented Jun 3, 2026 •
edited
Loading

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 114df0db-5892-445e-bc3b-e3c90d3df7d0

📥 Commits

Reviewing files that changed from the base of the PR and between 04de7eb and 52514e3.

📒 Files selected for processing (1)
  • .github/workflows/publish.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/publish.yaml
📝 Walkthrough

Walkthrough

Adds a latest-only workflow step that blocks publishing unless github.ref matches refs/(heads|tags)/release/*, and updates the latest channel Slack Linear-completion message to prepend a 🚀 emoji to “Release”.

Changes

Publish workflow updates

Layer / File(s) Summary
Validate release ref for latest channel
.github/workflows/publish.yaml		 New latest-only workflow step checks github.ref matches `refs/(heads
Update Slack release message text
.github/workflows/publish.yaml		 Slack payload text for the latest channel Linear-completion message changed from “Release” to “🚀Release”.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • agoldis
  • miguelangaranocurrents
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding validation to enforce that the 'latest' channel publishing is restricted to release/* branches.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch maxi/enforce-release-branch-for-latest-publish

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@maxigimenez maxigimenez requested a review from agoldis June 3, 2026 10:41
@miguelangaranocurrents miguelangaranocurrents merged commit f620c80 into main Jun 5, 2026
5 checks passed
@miguelangaranocurrents miguelangaranocurrents deleted the maxi/enforce-release-branch-for-latest-publish branch June 5, 2026 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@miguelangaranocurrents miguelangaranocurrents miguelangaranocurrents approved these changes

@agoldis agoldis Awaiting requested review from agoldis

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@maxigimenez @miguelangaranocurrents